kelvin Posted September 1, 2009 Report Posted September 1, 2009 hi support, we have map multiple DDIs to a single extension and this particular extension we added manual registration for relay to OCS2007. routing path as below. DDIs --> SIP --> Pbxnsip --> SIP --> OCS 2007 R2 When we call particular DDI, let said call DDI - 1111 but DDI - 2222, DDI - 3333 and so on... all DDI numbers will relay to OCS 2007 R2. OCS 2007 R2 receiving multiple SIP invite (we map 10DDIS, Pbxnsip will sent 10 SIP invite to OCS) please advise how can we configure to sent called DDI sip invite only. example: we call DDI - 2222 and pbxnsip only sent DDI - 2222 SIP invite only. regards, Kelvin Quote
Vodia PBX Posted September 2, 2009 Report Posted September 2, 2009 please advise how can we configure to sent called DDI sip invite only. example: we call DDI - 2222 and pbxnsip only sent DDI - 2222 SIP invite only. So you want to keep the DID (DDI?) from the incoming call? There is a setting in the domain that instructs the PBX to leave the names unchanged. That might help. Quote
kelvin Posted September 2, 2009 Author Report Posted September 2, 2009 So you want to keep the DID (DDI?) from the incoming call? There is a setting in the domain that instructs the PBX to leave the names unchanged. That might help. Support, the DID number unchanged, but pbxnsip sent multiple invite even we just called 1 DID number on. please looked below pbx log. we called DID +60327215891 but pbx sent all DID invite. we configure multiple DID in 1 extension. 2009/09/02 16:03:49: Trunk IN-Cisco-94 (global) sends call to 60327215891 in domain donotdelete.com [9] 2009/09/02 16:03:49: Resolve 653334: url sip:+60327215890@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653334: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653334: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653335: url sip:+60327215899@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653335: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653335: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653336: url sip:+60327215891@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653336: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653336: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653337: url sip:+60327215892@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653337: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653337: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653338: url sip:+60327215893@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653338: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653338: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653339: url sip:+60327215894@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653339: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653339: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653340: url sip:+60327215895@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653340: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653340: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653341: url sip:+60327215896@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653341: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653341: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653342: url sip:+60327215897@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653342: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653342: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653343: url sip:+60327215898@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653343: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653343: tcp 202.168.66.202 5060 [5] 2009/09/02 16:03:49: Identify trunk (IP address match) 11 Quote
pbx support Posted September 2, 2009 Report Posted September 2, 2009 Where are these DDIs assigned on the PBX? Also, can you please enable the SIP logging and send the trace to support@pbxnsip.com? (on how to enable the SIP tracing https://pbxnsipsupport.com/index.php?_m=kno...kbarticleid=58) Support, the DID number unchanged, but pbxnsip sent multiple invite even we just called 1 DID number on. please looked below pbx log. we called DID +60327215891 but pbx sent all DID invite. we configure multiple DID in 1 extension. 2009/09/02 16:03:49: Trunk IN-Cisco-94 (global) sends call to 60327215891 in domain donotdelete.com [9] 2009/09/02 16:03:49: Resolve 653334: url sip:+60327215890@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653334: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653334: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653335: url sip:+60327215899@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653335: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653335: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653336: url sip:+60327215891@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653336: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653336: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653337: url sip:+60327215892@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653337: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653337: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653338: url sip:+60327215893@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653338: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653338: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653339: url sip:+60327215894@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653339: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653339: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653340: url sip:+60327215895@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653340: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653340: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653341: url sip:+60327215896@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653341: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653341: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653342: url sip:+60327215897@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653342: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653342: tcp 202.168.66.202 5060 [9] 2009/09/02 16:03:49: Resolve 653343: url sip:+60327215898@mycybhpv02.my.tria.de;transport=tcp [9] 2009/09/02 16:03:49: Resolve 653343: a tcp mycybhpv02.my.tria.de 5060 [9] 2009/09/02 16:03:49: Resolve 653343: tcp 202.168.66.202 5060 [5] 2009/09/02 16:03:49: Identify trunk (IP address match) 11 Quote
kelvin Posted September 3, 2009 Author Report Posted September 3, 2009 Where are these DDIs assigned on the PBX? Also, can you please enable the SIP logging and send the trace to support@pbxnsip.com?(on how to enable the SIP tracing https://pbxnsipsupport.com/index.php?_m=kno...kbarticleid=58) hi support, we assigned in account number field by putting multiple value as below. i have emailed the log file. thanks +60327215890 60327215890 60327215891 60327215892 60327215893 60327215894 60327215895 60327215896 60327215897 60327215898 60327215899 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.