Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-23-2011, 05:44 AM
bestann bestann is offline
Hot Shot
 
Join Date: Aug 2010
Posts: 14
bestann has 10 reputation points
Default Avaya doesn't prepend + in sip trunk-group

CM 5.2.1 SP 7.1, S8730.

I don't see + in trace Prepend '+' to Calling Number? y:
Code:
change trunk-group 67                                           Page   4 of  21
                              PROTOCOL VARIATIONS

                      Mark Users as Phone? y
            Prepend '+' to Calling Number? y
      Send Transferring Party Information? y

                    Send Diversion Header? n
                  Support Request History? y
             Telephone Event Payload Type:
trace
Code:
15:53:15 SIP>INVITE sip:21171@192.168.180.22;user=phone SIP/2.0
15:53:15     dial 21171
15:53:15     seize trunk-group 67 member 17  cid 0x2549
15:53:15     Setup digits 21171
15:53:15     Calling Number & Name 21522 Toropova Anna
15:53:15 SIP<SIP/2.0 100 Trying
15:53:15     Proceed trunk-group 67 member 17  cid 0x2549  
....
15:53:16 SIP>ddr=192.168.180.22 SIP/2.0
15:53:16     denial event 1166: Unassigned number D1=0xe0011 D2=0x1
15:53:16     idle trunk-group 67 member 17  cid 0x2549
It adds + only if I enable IMS in sip signalling group:
Code:
15:42:53 SIP>INVITE sip:+21171@192.168.180.22 SIP/2.0
15:42:53     dial 21171
15:42:53     seize trunk-group 67 member 16  cid 0x1c27
15:42:53     Setup digits 21171
15:42:53     Calling Number & Name 21522 Toropova Anna
15:42:53 SIP<SIP/2.0 100 Trying
15:42:53     Proceed trunk-group 67 member 16  cid 0x1c27
15:42:53 SIP<SIP/2.0 488 MediationCall SetupCall error:  Mediati
15:42:53 SIP<onCall CreateOutgoingSession error.
15:42:53 SIP>ACK sip:+21171@192.168.180.22 SIP/2.0
15:42:53     denial event 1204: Bearer cap not implem D1=0xe0011 D2=0x41
15:42:53     idle trunk-group 67 member 16  cid 0x1c27
But I don't need IMS enabled because of bearer capability.

What shall I do to make Prepend '+' to Calling Number? y work?

I use OPS to ring 21171 and +21171 sip number simultaneously.

Last edited by bestann; 06-23-2011 at 10:42 AM.
Reply With Quote
  #2  
Old 08-04-2011, 10:12 AM
zhuayong zhuayong is offline
Member
.
 
Join Date: Jan 2011
Posts: 9
zhuayong has 10 reputation points
Default

Quote:
Originally Posted by bestann View Post
CM 5.2.1 SP 7.1, S8730.

I don't see + in trace Prepend '+' to Calling Number? y:
Code:
change trunk-group 67                                           Page   4 of  21
                              PROTOCOL VARIATIONS

                      Mark Users as Phone? y
            Prepend '+' to Calling Number? y
      Send Transferring Party Information? y

                    Send Diversion Header? n
                  Support Request History? y
             Telephone Event Payload Type:
trace
Code:
15:53:15 SIP>INVITE sip:21171@192.168.180.22;user=phone SIP/2.0
15:53:15     dial 21171
15:53:15     seize trunk-group 67 member 17  cid 0x2549
15:53:15     Setup digits 21171
15:53:15     Calling Number & Name 21522 Toropova Anna
15:53:15 SIP<SIP/2.0 100 Trying
15:53:15     Proceed trunk-group 67 member 17  cid 0x2549  
....
15:53:16 SIP>ddr=192.168.180.22 SIP/2.0
15:53:16     denial event 1166: Unassigned number D1=0xe0011 D2=0x1
15:53:16     idle trunk-group 67 member 17  cid 0x2549
It adds + only if I enable IMS in sip signalling group:
Code:
15:42:53 SIP>INVITE sip:+21171@192.168.180.22 SIP/2.0
15:42:53     dial 21171
15:42:53     seize trunk-group 67 member 16  cid 0x1c27
15:42:53     Setup digits 21171
15:42:53     Calling Number & Name 21522 Toropova Anna
15:42:53 SIP<SIP/2.0 100 Trying
15:42:53     Proceed trunk-group 67 member 16  cid 0x1c27
15:42:53 SIP<SIP/2.0 488 MediationCall SetupCall error:  Mediati
15:42:53 SIP<onCall CreateOutgoingSession error.
15:42:53 SIP>ACK sip:+21171@192.168.180.22 SIP/2.0
15:42:53     denial event 1204: Bearer cap not implem D1=0xe0011 D2=0x41
15:42:53     idle trunk-group 67 member 16  cid 0x1c27
But I don't need IMS enabled because of bearer capability.

What shall I do to make Prepend '+' to Calling Number? y work?

I use OPS to ring 21171 and +21171 sip number simultaneously.
Hi,

I guess there's a misunderstanding. The CM manual explains the meaning of Prepend "+" to Calling Number as follows:
If enabled, the calling party number in the header of the SIP message is prepended with a plus
sign (+). Available only for sip trunk groups.

In your trace, 21171 was the request-URI (called party number), instead of calling party number hence you will not see "+" in front of it.

If IMS is enabled on signaling group and you use public numbering in SIP trunk group, you will see "+" in front of the request-URI, this works as designed.

Hope it helps,

Regards,
Howard
Reply With Quote
  #3  
Old 08-15-2011, 04:23 PM
ahartoch ahartoch is offline
Guru
 
Join Date: Aug 2010
Location: Barcelona
Posts: 122
ahartoch has 10 reputation points
Default

try adding an entry in the public-unknown table
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:34 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.