locked
Dialogic gateway: No inbound calls after migrating from SIP control 1.5 to 1.6 RRS feed

  • Question

  •  

    I have migrated to SIP control 1,6 and realize it doesn't migrate all the configuration settings in a right way.  With SIP control 1.5 in- and outbound calls were working fine.

     

    I'm getting the "invalid number" message in my phone when I call the auto attendant or an internal user.

    Outgoing calls from OCS are working fine. Incoming calls are reaching the gateway (it's being logged). When it reaches the Mediation server I'm getting an error.

     

     9:24:46.178 0 L 12 00010000-SIPR begin (396 byte) from IP:172.19.160.21 PORT:5060 on socket 2 port 5060 TCP
     9:24:46.178 0 L 12 00010000-    >SIP/2.0 404 Not Found
     9:24:46.178 0 L 12 00010000-    >FROM: "Dialogic Diva SIPcontrol"<sip:+31347621537161@172.19.160.70;user=phone>;tag=sipcontrol_227564552-1512420
     9:24:46.178 0 L 12 00010000-    >TO: "Default"<sip:+31347347324150@172.19.160.21;user=phone>;tag=66194175a2
     9:24:46.178 0 L 12 00010000-    >CSEQ: 1 INVITE
     9:24:46.178 0 L 12 00010000-    >CALL-ID: d905c08-1513e4-4@sgtw0001sel
     9:24:46.178 0 L 12 00010000-    >VIA: SIP/2.0/TCP 172.19.160.70:9801;branch=z9hG4bK227564552-1446884
     9:24:46.178 0 L 12 00010000-    >CONTENT-LENGTH: 0
     9:24:46.178 0 L 12 00010000-    >SERVER: RTCC/3.0.0.0 MediationServer
     9:24:46.178 0 L 12 00010000-    >
     9:24:46.178 0 L 12 00010000-SIPR end

     

     

    I was playing around with the SIP peer settings and try to configure it in this way that it doesn't modify the incoming number. Sofar there was no result (after saving and restarting the configuration/server). Dailing rules are not changed after migrating.

     

    I have also checked the PSTN listening ports on the mediation server (which is on a different box) and that has been setup correctly (in fact there were no changes on that side). Connectivity between the gateway and the mediation server is also fine (not firewalled).

    So I'm focussing on how the number will be send to the Mediation server from the gateway. With the previous version of SIP control I was able to set the number format (E 164). Where can I do this in SIP control version 1.6?

     

    I'm sure it's a simple setting somewhere to get it working again.

     

    Help and suggestions are appreciated!

    Tuesday, March 11, 2008 7:00 PM

Answers

  • Problem solved.

    I was submitting a post on the Dialogic forum and got some usefull suggestions.

    "Generally the upgrades from 1.5 to 1.6 go smoothly, the exception being if you had complex rules defined in the registry which most users didn't.
    1.6 is a more powerful but more complex interface so what I I would suggest you do is to go back to 1.5, configure it as you had it before then upgrade to 1.6 and then we will have a solid platform to work with.

    To downgrade just uninstall 1.6.
    Then delete any sip*.xml files in Program files\Diva Server.
    Now install 1.5 again and configure.
    Once 1.5 is configured and working just upgrade to 1.6.

    This sounds a long way round but takes about 5 minutes and is generally worth it.

    To signal the number to OCS in E.164 format then in the Sip Peer/Address Normalisation field set the Number format(Outbound) to 'International Number' and Encoding(Outbound) to 'Use Type Flag'.
    International will make the number E.164 and type flag will add a + for Sip calls.
    This should be the default after an upgrade.

    Sending the the N will result in OCS rejecting the call, again the upgrade would have put some rules in to remove this by default.

    If 1.6 is still not working after the upgrade then please post a trace of a full call here. "

    After changing (in the SIP Peer settings) the Number format (outbound) to International Number and Encoding (Outbound) to Use type flag I realized that I got a very long number in my trace log.

    Looking at the Dailplan I saw that the Area code entry (0347) and the base number entry were filled up. after removing those entries (and only leaving the country code and national prefix) I was able to dail in again via the gateway.

    I know that I was not changing any settings after migrating to the 1.6 version of SIP control so in my case it didn't migrate the settings in a proper way. This gateway is a test gateway directly connected to an ISDN line (without a PBX in front). Probably this could be the reason why the dailplan setting were filled up differently after migrating.

    I will check this with the Dialogic guys. Anyway when can continue testing with the new SIP control version!


    Wednesday, March 19, 2008 5:24 PM

All replies

  • Can you verify that the user you are trying to call has exactly this number in its Line URI

    tel:+31347347324150

     

    You gateway might be adding to many numbers?

     

    Johan

    Tuesday, March 11, 2008 10:05 PM
  • You are absolutely right! ...this doesn't seem correct.. I'll have a look at it right away...
    Wednesday, March 12, 2008 7:14 AM
  • I was playing around with some settings in the SIP control web console. It was sending an incoming call in the following format to the mediation server: '34xxxxxxx'. In the previous SIP control version I was able to set the signal number in E 164 format. In this case it was sending the full number with international access code to the medaition server. In the current SIP control version I'm not able to do this anymore.

    So I was focussing on the address map configuration. After adding some "AddressMapInGlobale" rules the local number will be sent to the mediation server with a 'N' in front : 'N34xxxxxxx'.  It is recognizing this call as a local number wich is correct. Now the medaition server doesn't seem to recognize this format. Do I have the add a dailing rule in OCS to handle this format or can I just send the number in E 164 like I used to do using SIP control 1.5?
    Monday, March 17, 2008 7:25 AM
  • OCS only works with E.164 numbering.

    So you need to change the gateway configuration.

     

    I don't know the Sip Control software so you might need to contact Dialogic Support

     

    Johan

    Monday, March 17, 2008 5:14 PM
  • Problem solved.

    I was submitting a post on the Dialogic forum and got some usefull suggestions.

    "Generally the upgrades from 1.5 to 1.6 go smoothly, the exception being if you had complex rules defined in the registry which most users didn't.
    1.6 is a more powerful but more complex interface so what I I would suggest you do is to go back to 1.5, configure it as you had it before then upgrade to 1.6 and then we will have a solid platform to work with.

    To downgrade just uninstall 1.6.
    Then delete any sip*.xml files in Program files\Diva Server.
    Now install 1.5 again and configure.
    Once 1.5 is configured and working just upgrade to 1.6.

    This sounds a long way round but takes about 5 minutes and is generally worth it.

    To signal the number to OCS in E.164 format then in the Sip Peer/Address Normalisation field set the Number format(Outbound) to 'International Number' and Encoding(Outbound) to 'Use Type Flag'.
    International will make the number E.164 and type flag will add a + for Sip calls.
    This should be the default after an upgrade.

    Sending the the N will result in OCS rejecting the call, again the upgrade would have put some rules in to remove this by default.

    If 1.6 is still not working after the upgrade then please post a trace of a full call here. "

    After changing (in the SIP Peer settings) the Number format (outbound) to International Number and Encoding (Outbound) to Use type flag I realized that I got a very long number in my trace log.

    Looking at the Dailplan I saw that the Area code entry (0347) and the base number entry were filled up. after removing those entries (and only leaving the country code and national prefix) I was able to dail in again via the gateway.

    I know that I was not changing any settings after migrating to the 1.6 version of SIP control so in my case it didn't migrate the settings in a proper way. This gateway is a test gateway directly connected to an ISDN line (without a PBX in front). Probably this could be the reason why the dailplan setting were filled up differently after migrating.

    I will check this with the Dialogic guys. Anyway when can continue testing with the new SIP control version!


    Wednesday, March 19, 2008 5:24 PM
  • As a follow-up in case anyone else has a similar issue, I posted some further advice on configuring SIP Control (as used in DMG3000 and DMG4000 gateways) here:

     http://www.dialogic.com/forums/forums/thread-view.asp?tid=2714&posts=5&start=1

    Tuesday, March 25, 2008 11:21 AM